-
Notifications
You must be signed in to change notification settings - Fork 203
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade to ivy #509
base: master
Are you sure you want to change the base?
Upgrade to ivy #509
Conversation
Is anything blocking this PR? We also need this merged or supported in any way ASAP due to Angular 16 arriving soon. |
This is currently blocking us from upgrading to Angular 16 which does not support ViewEngine libraries anymore. I would highly appreciate releasing this change :) |
Do we have updates about this one? Angular 16 has been released and it will not support ViewEngine libraries anymore. |
Is there any update or work around ?unable to use froala with angular 16 |
Our team is also waiting for this in order to updrage Angular version 16. |
Any updates? Need this change badly |
Our team is also blocked by this |
We cannot upgrade to Angular 16 because of that. Please resolve asap. |
For everyone who wants a workaround here you will have one #505 (comment) but you are loosing all the updates. I have heard that the Froala team will come with something in the near future. But in the meanwhile you can use the workaround and enjoy angular 16 |
An alternative approach that I went for is to just copy the respective files and put them into your project directly. In the end, this library is "just" a wrapper around the I will definitely keep my eyes open for future updates of |
Change the builder to ivy to be compatible with angular 15. It is a breaking change since it can't be used with the view engine anymore. Related to #505